objmem: prevent calling audio_RemoveObj()
from the destructors of in-game objects
#4033
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The call to
audio_RemoveObj
inside the destructors ofSIMPLE_OBJECT
,DROID
,STRUCTURE
,FEATURE
andPROJECTILE
classes can possibly invoke undefined behavior if the warzone process is being forcefully shut down (either by us, the user or some other third-party code, like X11 in case of linux).The reason for this is that by the time a given game object is being destroyed, chances are that the static objects from the audio code, which are being accessed by the
audio_RemoveObj()
, can already be destroyed (due to the inverse of the Static initialization order fiasco).Signed-off-by: Pavel Solodovnikov [email protected]